Managing notifications of a delivery method based on an active device

ABSTRACT

Techniques for managing notifications may be described. In an example, the notifications may relate to an item and may be provided to a user device. An active device may be associated with the item. The active device may store a token for communication with a local area network associated with a location. Based on the communication, a determination may be made that the item may be in proximity to the location. Corresponding notifications may be sent to the user device.

BACKGROUND

More and more users are turning to network-based resources, such asweb-based resources that may utilize the Internet, to order items (e.g.,goods and/or services). A network-based resource may provide a userexperience unmatched by a more traditional brick and mortar store. Forexample, the network-based resource may offer a larger and more diverseselection of items. Further, for some of the items, there may be anumber of sellers with different offers. As such, a customer may notonly have access to a rich item selection, but may also obtain items atthe most convenient offers.

Typically, a user device and a network-based resource may interact toexchange information about items. The interactions may includenotifications provided to the user device. A notification may relate toan item, such as a delivery status of the item. The number, content, andtimings of the notifications may affect the user experience, networkbandwidth, processing of network-based resource, and/or processing ofthe user device.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments in accordance with the present disclosure will bedescribed with reference to the drawings, in which:

FIG. 1 illustrates an example computing environment where notificationsmay be transmitted, according to a particular embodiment;

FIG. 2 illustrates an example computing environment that may utilize adestination delivery management device, according to a particularembodiment;

FIG. 3 illustrates example notifications available from a computingenvironment utilizing a destination delivery management device,according to particular embodiments;

FIG. 4 illustrates an example computing environment that may utilize anactive device, according to a particular embodiment;

FIG. 5 illustrates example notifications available from a computingenvironment utilizing an active device, according to a particularembodiment;

FIG. 6 illustrates an example flow for providing notifications,according to a particular embodiment;

FIG. 7 illustrates an example flow for providing notifications in acomputing environment utilizing a destination delivery managementdevice, according to a particular embodiment;

FIG. 8 illustrates another example flow for providing notifications in acomputing environment utilizing a destination delivery managementdevice, according to a particular embodiment;

FIG. 9 illustrates an example flow for providing notifications in acomputing environment utilizing an active device, according to aparticular embodiment;

FIG. 10 illustrates another example flow for providing notifications ina computing environment utilizing an active device, according to aparticular embodiment; and

FIG. 11 illustrates example end-to-end architecture for facilitating anelectronic marketplace, according to a particular embodiment.

DETAILED DESCRIPTION

In the following description, various embodiments will be described. Forpurposes of explanation, specific configurations and details are setforth in order to provide a thorough understanding of the embodiments.However, it will also be apparent to one skilled in the art that theembodiments may be practiced without the specific details. Furthermore,well-known features may be omitted or simplified in order not to obscurethe embodiment being described.

Embodiments herein are directed to managing notifications within acomputing environment. In an example, the computing environment mayinclude a network-based resource accessible to a user device over anetwork. The network-based resource may be configured to providenotifications to the user device. The notifications may relate to anitem. Unlike many traditional computing environments, the notificationsmay be provided in real-time based on triggers (e.g., within a shortperiod of time after an occurrence of a trigger). An example trigger mayinclude a state or a change in the state of the item. Another exampletrigger may include a request from the user device. Regardless of thetriggers, the notifications may be based on real-time data about theitem. Because of the real-time data, the notifications may providemeaningful information about the item, rather than outdated or staleinformation. In addition, because of the triggers, only the necessary ordesired number of notifications may be provided to the user device,rather than a flood of unnecessary or unwanted notifications.Accordingly, the user experience may be enhanced while also the usage ofcomputing resources within the computing environment and the usage ofthe network bandwidth may be reduced. To trigger real-timenotifications, the item may be associated with a notification device,such as a label capable of data exchange. The association may include adirect physical attachment between the item and the notification deviceor an indirect attachment through an intermediary holder. In turn, thenotification device may be configured to connect to the network throughvarious computing devices. Communications with the computing devices maytrigger the notifications in real-time.

To illustrate, consider a first example of an electronic marketplace. Auser may operate a user device to order, such as for rent or purchase,an item. The item may be delivered from a source to a destination via adelivery vehicle. A holder, such as a package, may retain the item forthe delivery. A passive radio frequency identification (RFID) tag may beattached to the package and may uniquely identify the order. Whenloading the item onto the delivery vehicle, a handheld device may readthe RFID tag. The handheld device may be connected over a network to acomputer system of the electronic marketplace. The reading of the RFIDtag may identify the item causing the handheld device to indicate to thecomputer system that the loading has occurred. In response, the computersystem may send a notification about a start of the delivery to the userdevice. While the item is in route, the user device may access thecomputer system to request location information about the item. Inresponse, the computer system may use the handheld device's and/or thedelivery truck's global positioning system (GPS) data to estimate andprovide the location information to the user device. Upon arrival to thedestination, a computing device located at the destination may connectto the handheld device and/or read the RFID tag. The computing devicemay also connect to the computer system over a network and may haveaccess to information about the order. Accordingly, the computing devicemay authorize the handheld device to drop-off the item at thedestination and may cause a notification about the drop-off to be sentto the user device. Further, the computing device may be configured todetermine movement and/or pick-up of the item. As such, once the itemhas been dropped-off, any movement and/or pick-up of the item maytrigger a corresponding notification to be sent to the user device.

In another illustration, consider a second example of a same or adifferent electronic marketplace. In this example, an active 802.11 RFIDtag may be utilized in lieu or in addition to the passive RFID tag. Uponarrival, the active 802.11 RFID tag may connect to a computing node(e.g., an access point or an intermediary computing device) of a localarea network of the destination. The active 802.11 RFID tag and thecomputing node may utilize a token to establish communication. The tokenmay be based on the order of the item. Similarly, the handheld devicemay communicate with the computing node. Based on the communication ofthe handheld device and/or the active 802.11 RFID tag with the computingnode, the drop-off may be determined and the respective notification maybe sent to the user device. Subsequent to the drop-off, thecommunication between the active 802.11 RFID tag and the computing nodemay be utilized to determine movement and/or pick-up of the item and to,accordingly, send the respective notifications to the user device.

In the interest of clarity of explanation, embodiments may be describedherein in connection with an electronic marketplace. However, theembodiments may not be limited as such. Instead, the embodiments maysimilarly apply to any computing environment where notifications may begenerated and provided. For example, the embodiments may similarly applyto an inventory system, a tracking system, and/or any other environmentwhere notifications may be provided from computing resource to a userdevice, such as from a server to a client.

Turning to FIG. 1, the figure illustrates an example computingenvironment for providing notifications. In particular, the computingenvironment may include a computer system 110 and a user device 120exchanging information about an item 130 over a network 140. In anexample, the computer system 110 may facilitate functionalities of anelectronic marketplace offering the item 130. The user device 120 mayaccess the computer system 110 to order the item 130. Different ordertypes may be supported such as purchasing, renting, leasing, selling,and/or returning the item 130. A delivery of the item from a source 112to a destination 150 may be performed based on the order. The deliverymay utilize a delivery vehicle 160. Notifications 122 about the item130, such as ones related to the order and the delivery, may be providedto the user device 120. The notification 122 may be triggered by and/ormay utilize real-time data. Each of these components is described hereinnext.

In the interest of clarity of explanation, the embodiments of thepresent disclosure may be described in connection with a delivery fromthe source 112 to the destination 150. This may correspond to, forexample, a purchase of the item 130 for delivery to the destination 150.However, the embodiments are not limited as such. Instead, theembodiments may similarly apply to a delivery from the destination 150to the source 112. This may correspond to, for example, a return or asale of the item 130 for delivery to the source 112.

In an illustrative example, the source 112 may represent a fulfillmentcenter (F.C.) associated with the electronic marketplace. Thefulfillment center may include a warehouse, a storage facility, or someother source from which the item may be available or to which the itemmay be returned. Generally, the electronic marketplace may offer andfacilitate orders and deliveries of the item (or units thereof) from andto the source 112.

The destination 150 may represent a location to which the item 130 maybe delivered (or, conversely, from which the item 130 may be picked up).For instance, the destination 150 may represent a house, a store, astreet intersection, or other delivery locations. Further, thedestination 150 may include a local area network of one or morecomputing nodes that may be, in turn, connected to the computer system110 over the network 140.

The computer system 110 may include a number of computing resources,such as servers or a server farm, configured to facilitate thefunctionalities of the electronic marketplace. For example, the computersystem 110 may host an electronic platform. The electronic platform mayinclude a front end system, such as a web site of the electronicmarketplace, to offer items and different delivery methods. A useroperating a user device may interact with the front end system to orderavailable items and select delivery methods. The electronic platform mayalso include a back end system to process and manage deliveries ofitems.

The user device 120 may include any suitable computing device capable ofcommunicating with the computer system 110 over the network 140. Forexample, the user device 120 may include a number of general purposepersonal computers, such as desktop or laptop computers running astandard operating system, as well as cellular, wireless, and handhelddevices running mobile software and capable of supporting a number ofnetworking and messaging protocols.

The network 140 may include any one or a combination of many differenttypes of networks. For example, the network 140 may include any ofwireless networks, cable networks, cellular networks, radio networks,the Internet, and other private and/or public networks.

The item 130 may be available from the electronic marketplace and mayinclude a tangible item (e.g., a physical item such as a camera or amultimedia file) or an intangible item (e.g., a service to be providedat the destination 150). As part of the delivery, the item 130 may beheld in a holder, such as in a suitable package. Suitable packagesexemplified by item 130 may include a box, a bin, a tote, a bag, oranother receptacle of proper structure and material.

The delivery vehicle 160 may represent a vehicle for delivering the item130 from the source 112 to the destination 150. The delivery vehicle 160may be manually, remotely, semi-autonomously, or autonomously operatedand may include a ground, air, and/or water-based vehicle. In addition,the delivery vehicle 160 may connect to the computer system 110, theuser device 120, and/or the destination 150 (e.g., a computing node atthe destination 150) over the network 140.

Further, a delivery device 162 may be associated with the deliveryvehicle or an operator of the delivery vehicle. For instance, thedelivery device 162 may be integrated with the delivery vehicle 160 ormay be a handheld device that may be stored at and utilized inconjunction with the delivery vehicle 160. The delivery device 162 mayinclude a computing device that may connect to the computer system 110,the user device 120, and/or the destination 150 (e.g., a computing nodeat the destination 150) over the network 140. In addition, the deliverydevice 162 may include different interfaces related to the delivery ofthe item 130. One example interface may include a reader for accessinginformation about the item 130 (e.g., a reader that may interact with atag attached to the holder of the item). Another example interface mayinclude an interface configured to provide, such as to display to anoperator and/or transmit to the delivery vehicle 160, deliveryinstructions and to receive responses to the delivery instructions fromthe operator and/or delivery vehicle 160.

The user device 120 may receive the notification(s) 122 from thecomputer system 110, the destination 150 (e.g., a computing node at thedestination 150), the delivery vehicle 160, and/or the delivery device162 over the network 140 (or some other network). Generally, thenotifications 122 may provide information about the item 130, such asabout the order and/or the delivery thereof. In an example, anotification may include information about a location of the item, atime associated with the location of the item, a state of the item, theorder, and/or delivery. Some of the notifications 122 may be triggeredby a change of the state of the item 130, the order, and/or thedelivery. Other notifications 122 may be requested by the user device120 from the computer system 110, the destination 150 (e.g., a computingnode at the destination 150), the delivery vehicle 160, and/or thedelivery device 162. FIG. 1 illustrates five notifications 122, althougha different number of notifications 122 may exist. Each of the fivenotifications 122 may have been provided in real-time to the user device120 (e.g., within a short period of time after occurrence of arespective trigger). A first notification may correspond to the item 130arriving to a location “A,” such as when the item 130 may have beenloaded onto the delivery vehicle 160 which may represent a start of thedelivery. A second notification may correspond to the item being droppedoff at the destination 150. A third notification may describe that theitem 130 may have been moved since the drop-off. A fourth notificationmay describe an environment condition at the destination 150 and mayrecommend a corresponding action related to the delivery (e.g., to movethe item 130 because of rain). A fifth notification may indicate thatthe item 130 may have been picked up.

To provide the notifications 122, a tag may be attached to the item 130and/or to the holder of the item 130. A proximity of the tag with thedelivery device 162 and/or the destination 150 (e.g., a computing nodeof the destination 150) may trigger the notifications. In an example,the proximity may be based on wired, wireless, radio frequency (RF),optical, and/or other type of communications between the tag, thedelivery device 162, and/or the destination 150.

Different embodiments of the tag may be implemented. Generally, theembodiments may balance between cost, processing capabilities, and/orpower consumption of the tag versus cost and/or processing capabilitiesof the delivery device 162 and/or of the computing node of thedestination 150. FIG. 2 illustrates an example of a tag as a passivedevice, where the cost, processing capabilities, and power consumptionof the passive device may be reduced. Instead, processing related to thenotifications may be pushed to the delivery device 162 and/or thecomputing node of the destination 150. In comparison, FIG. 4 illustratesan example of an active device as an implementation of the tag. In thisexample, some of the cost, processing, and/or power may be pushed to theactive device.

An example of the passive device is illustrated in FIG. 2. Inparticular, a passive device 210 may be attached, via adhesion or someother attachment means, to a holder 212 of an item (or to the itemitself). The passive device 210 may represent a printable passive RFIDtag that may encode information, such as a unique identifier(s), aboutthe item, the delivery (e.g., delivery location and/or deliveryinstructions), and/or an order of the item. Other types of passivedevices may be used. For example, one or two dimensional barcodes may beused.

Upon the order of the item, a computer system 220, similar to thecomputer system 110 of FIG. 1, may provide instructions for configuringthe passive device 210. The instructions may include the information tobe encoded in the passive device 210. Once configured (e.g., printed inthe case of a printable passive RFID tag), the passive device 210 may beattached to the holder 212. Further, the computer system 220 may providesome or all of the encoded information to a delivery device 230 and/orthe destination 240 (e.g., to a computing node thereof). The deliverydevice 230 and the destination 240 may be similar to the delivery device162 and the destination 150 of FIG. 1, respectively. The information maybe pushed or transmitted upon request over a network 250.

The destination 240 may include a local area network 242, such as awireless local network interconnecting various computing nodes locatedat the destination 240 (e.g., inside or within a geographical fence ofthe destination 240). The local area network 242 may also be connectedto the network 250 such that a communication path may exist between thecomputing nodes and the computer system 220, the delivery device 230,and/or a user device 260. These computing nodes may include, forexample, an access point, a router, and/or other computing resources. Inaddition, the computing nodes may include a delivery management device244. The delivery management device 244 may represent a computing devicethat may be configured to manage part of the delivery of the item toand/or from the destination 240 (e.g., a drop-off and/or a pick-up atthe destination 240).

In an example, the delivery management device 244 may include aprocessor, a memory, and other computing components implemented inhardware and software. These computing components may include, forinstance, a GPS receiver, a radio frequency (RF) transceiver, a wirelessor wired data interface, a user interface, a weight sensor, a pressuresensor, an optical sensor, an environment sensor (e.g., a rain sensor),and/or a delivery management module. The delivery management module maybe configured to request and/store information about the passive device210, the computer system 220, the item, the delivery, the deliverydevice 230, and/or the user device 260 and to manage interactions withthe passive device 210, the computer system 220, the delivery device230, and/or the user device 260. These interactions may use the variouscomponents of the delivery management device 244.

Other configurations of the delivery management device 244 may be used.For example, some of the components, whether hardware or software, maybe pushed to other computing nodes of the local area network or to thecomputer system 220. For instance, the delivery management device 244may include an interface for interfacing with the delivery device 230(e.g., an RFID tag, a barcode, etc.), a processor, a memory, and awireless transceiver to interface with the local area network 242. Inthis configuration, the delivery management device 244 may facilitatedata exchange between the delivery device 230 and a computing node(s) ofthe local area network 242. As such, much of the processing may bedistributed between the delivery device 230 and the computing noderather than being performed locally by delivery management device 244.

In operation, various notifications may be generated based on proximityof the different components. These notifications may relate to eventsassociated with the delivery. For example, the notifications may includeinformation about different delivery events upon occurrences of suchevents including a start of the delivery, a drop-off of the item, amovement of the item, and/or a pick-up of the item.

Upon a start of the delivery, the delivery device 230 may interact withthe passive device 210 to receive information therefrom. The interactionmay depend on the implementation of the passive device 210. Forinstance, the delivery device 230 may radiate a passive RFID tag with RFenergy and receive an RF signal in response from the passive RFID tag.In an example, upon interacting with the passive device 210, thedelivery device 230 may send the information included in the RF signalto the computer system 220 that may, in turn, send a notification aboutthe start of the delivery to the user device 260. In another example,the delivery device 230 may send the notification to the user device 260independently of the computer system 220.

While in route to the destination 240, the computer system 220 mayreceive the GPS location of the passive device 210 and/or the deliverydevice 230 and may provide such information to the user device 260. Uponarrival at the destination 240, the delivery device 230 may access theGPS location of the delivery management device 244, thereby allowing thedelivery device 230 to move to a proximity of the delivery managementdevice 244.

Once in proximity, various types of notifications may be generated basedon the interactions of the delivery management device 244 with thepassive device 210, the holder 212, and/or the delivery device 230. Theinteractions may be triggered by a request from the delivery device 230to the delivery management device 244. In another example, theinteractions may be triggered by the computer system 220. For instance,the computer system 220 may determine that the delivery device 230 maybe within a geographical fence of the destination 240. Accordingly, thecomputer system 220 may instruct the delivery management device 244 toping the passive device 210 (e.g., radiate a passive RFID tag with RFenergy) and/or establish a communication link with the delivery device230. Alternatively to using location information, the computer system220 may estimate a time window within which the delivery device 230 mayarrive to the destination 240 and may accordingly instruct the deliverymanagement device 244 in order to initiate the interaction. In yetanother example, the delivery management device 244 may trigger theinteractions independently of the computer system. For instance, thedelivery management device 244 may repeatedly generate a ping. Upon aresponse to a ping from the passive device 210, the delivery managementdevice 244 may establish a communication link with the delivery device230.

Once the interactions may be possible, different notifications may begenerated. In an example, the notifications may be generated by thedelivery management device 244 and/or the delivery device 230. Inanother example, the notifications may be generated by the computersystem 220 in response to the interactions. Once generated, thenotifications may be provided to the user device 260. In an example, thecomputer system 220 may send the notifications to the user device 260.In another example, the delivery management device 244 and/or thedelivery device 230 may send the notifications to the user device 260independently of the computer system 220.

The notifications may include an authorization of a drop-off of the item(or the holder 212), information about the drop-off, a lack of thedrop-off, and/or information about a virtual signature related to thedrop-off In an example, the delivery management device 244 may accessinformation from the passive device 210 (e.g., by reading the passiveRFID tag). In another example, the delivery management device 244 mayreceive the information over a communication link with the deliverydevice 230. The information may identify the order, the item, thepassive device 210, the delivery device 230, and/or the deliverymanagement device 244. In turn, the delivery management device 244(e.g., the delivery management module thereof) may access deliveryinformation from the computer system 220 or from the user device 260(e.g., upon a previous push or based on a request). The deliveryinformation may similarly identify the order, the item, the passive RFIDtag, and/or the delivery device 230 and may include deliveryinstructions (e.g., any needed signature of a user, delivery timewindow, special instructions, etc.). Based on a comparison, the deliverymanagement device 244 may authorize (or reject) the delivery andaccordingly transmit instructions to the delivery device 230. Inresponse, the delivery device 230 may display the authorization (or lackthereof) and any delivery instructions to an operator or may providesuch information to a computing device associated with a deliveryvehicle.

The delivery instructions may provide information about the delivery ofthe item at the destination 240. The computer system 220 and/or the userdevice 260 may provide the delivery instructions to the deliverymanagement device 244 and/or the delivery device 230. Different types ofdelivery instructions may exist. In an example, the deliveryinstructions may be defined at a user account level. For instance, theuser device 260 may be associated with a user account. As part ofsetting up or updating the delivery management device 244 and/or theuser account, the delivery instructions may be defined. In this example,the delivery instructions would apply to all deliveries unless indicatedotherwise. In another example, the delivery instructions may be definedat an item level. For instance, the user may specify that for any timethe item is ordered, the delivery instructions would be automaticallyapplied. In yet another example, the delivery instructions may bedefined at an order level. For instance, each time an order is made,specific delivery instructions may be defined for that order.

In addition, the delivery management device 244 and/or the computersystem 220 may update the delivery instructions over time. In anexample, the update may be based on an analysis of the history ofdeliveries. The analysis may include an optimization over one or moredelivery-related parameters. For instance, the analysis may consider thehistory to determine a time frame and/or location at the destination 240for dropping off the item. The time frame and/or location may reduce therisk of theft, loss, or damage to the item, increase the likelihood of aspeedy pick-up, and/or increase the likelihood of the user being presentat the time of the drop-off To illustrate, if the history indicates thata first drop-off location within a first time frame may have resulted inpast delivery thefts, but that a second drop-off location within asecond time frame may have resulted in a successful delivery, thedelivery instructions may be updated to schedule a delivery that mayavoid the first drop-off location and first time frame and that may takeadvantage of the second drop-off location and second time frame.Similarly, if the history indicates that deliveries within a particulartime frame, relative to other time frames, have resulted in a speedypick-up or that the user may have been present at the destination 240,the delivery instructions may be updated to use the particular timeframe.

In another example, the update to the delivery instructions may also oralternatively be based on an analysis of a history of deliveries, ahistory of delivery instructions, or delivery patterns within an areathat may include the delivery location. The area may correspond tolocations within a predetermined distance (e.g., relative to athreshold, such as a block, a hundred yards, etc.) from the deliverylocation. For instance, if the history indicates theft in the area, thedelivery instructions may necessitate a signature of a person at thedelivery location, provide information about a different, more securelocation for the drop-off, and/or reject the delivery. Similarly, if apredefined delivery locker is in the area, the delivery instructions maydefault to delivering the item to that location if it is not possible ornot safe to complete the delivery with respect to the delivery location.

Further, the delivery management device 244 and/or the computer system220 may update the delivery instructions based on parameters of acurrent delivery. For example, if the current delivery was notsuccessful (e.g., the item was not dropped-off or the item was stolen),the delivery instructions may be automatically updated to rescheduleanother delivery. In an example, the update may be based on the historyof deliveries as described herein above. In another example, the updatemay be based on settings or preferences of the user account.

The detection of a drop-off may use the proximity of the deliverymanagement device 244 to the passive device 210 and/or the deliverydevice 230. In an example, the delivery management device 244 mayincrease the RF ping rate. Upon receiving an RF response from thepassive device 210 for a predefined period of time (e.g., for fiveminutes), a drop-off may have occurred. In another example, the weightsensor and/or the pressure sensor may sense the holder 212, which mayindicate that a drop-off may have occurred. In another example, an inputindicating a drop-off may be received at a user interface of thedelivery management device 244. This input may be provided by anoperator of the delivery device 230. In another example, a userinterface (or some other interface) of the delivery device 230 mayreceive an indication of the drop-off (from the operator or from thedelivery vehicle) and may send this indication to the deliverymanagement device 244. In yet another example, by detecting theproximity of the passive device (e.g., based on the RF ping or thesensors) and by establishing the communication with the delivery device230, the delivery management device 244 may detect the drop-off.

The detection of a lack of a drop-off may also use the proximity of thedelivery management device 244 to the passive device 210 and/or thedelivery device 230. In an example, upon a proximity of the deliverymanagement device 244 and the delivery device 230, the deliverymanagement device 244 may send an RF ping. If no response from thepassive device 210 is received, the delivery management device 244 maydetect that no drop-off has occurred. Accordingly, a notification aboutthe lack of drop-off may be generated. In addition, in this case thedelivery management device 244 may perform an automatic action. Such anaction may be defined in the delivery instructions. For example, thedelivery management device 244 may re-order the item with an expeditedship method, reschedule a delivery, or request a refund.

The virtual handoff may be detected based on interactions between thedelivery management device 244 and the delivery device 230. For example,the delivery device 230 may request a virtual signature from thedelivery management device 244. Upon detecting the drop-off, thedelivery management device 244 may respond with the virtual signature.In another example, upon detecting the drop-off and once thecommunication with the delivery device 230 terminates (e.g., because ofphysical distance), the delivery management device 244 may determinethat the virtual handoff may have occurred.

Subsequent to the delivery device 230 departing from the destination 240and/or the termination of any communication with the delivery managementdevice 244, notifications about movement, lack of movement, relevantenvironmental conditions, and/or a pick-up of the item (or the holder212) may be provided. In an example, the delivery management device 244may generate these notifications. In another example, the deliverymanagement device 244 may provide relevant information to the computersystem 220 to generate the notifications. Once generated, the userdevice 260 may receive the notifications from the computer system 220and/or from the delivery management device 244 independently of thecomputer system 220.

Various techniques may be used to detect a movement of the item. In anexample, RF ranging may be used. For example, the delivery managementdevice 244 may estimate a proximity (e.g., a distance range) to thepassive device 210 based on a response to an RF ping. If that proximitychanges between two RF pings (e.g., based on signal strength of the RFsignal response from the passive device 210), the movement may bedetected. In addition, if an RF response is no longer received, thedelivery management device 244 may detect that the item may havedeparted from the geographical fence of the destination 240 (unless apick-up may have occurred). In another example, the weight and/orpressure sensors may be used to detect movement of the item. Forinstance, any change in the sensed data (e.g., pressure no longersensed) may indicate that the item may have been moved.

In addition to movement, lack of movement may also be determined as adelivery event. A corresponding notification may be provided to the userdevice 260. For instance, if after drop-off, the item is not picked-upwithin a time period, a notification may be generated. The time periodmay be defined based on different parameters. An example parameter mayinclude the item itself. For instance, if the item is a grocery item(s)(e.g., ice cream, a frozen entrée, or milk), that time frame may beshorter relative to other types of items. Similarly, if the item has avalue that exceeds a threshold, the time frame may be shorter relativeto less valuable items.

Similarly, various techniques may be used to detect an environmentalcondition that may impact the item. In an example, environmental sensors(e.g., rain or moisture sensors, humidity sensors, temperature sensors,light sensors, optical sensors, etc.) of the delivery management device244 may detect the environmental condition. In another example, thedelivery management device 244 may access environmental informationabout the location of the delivery management device 244 from a web siteover the network 250 to determine the environmental condition. If thiscondition is detected prior to a pick-up, the delivery management device244 may access (locally or remotely from the computer system 220) arecommendation related to the item delivery to be provided to the userdevice 260 (e.g., a recommendation for a pick-up within a time frame, tomove the item to a covered area, etc.).

Various techniques may also be used to detect a pick-up. In one example,an indication of the pick-up may be received at a user interface of thedelivery management device 244 or remotely from the user device 260. Inanother example, the pick-up may be determined based on the proximitybetween the delivery management device 244 and the user device 260. Forinstance, the computer system 220 may detect the proximity based on theGPS locations of the delivery management device 244 and the user device260. Additionally or alternatively, the delivery management device 244may receive the GPS location of the user device 260 from the computersystem 220 or from the user device 260 independently of the computersystem 220. Based on the proximity and a movement of the item, thedelivery management device 244 may determine that a pick-up may haveoccurred.

The delivery management device 244 may also include or interface withoptical sensors. The optical sensors may form an imaging device. Thedelivery management device 244 and/or the computer system 220 maytrigger the imaging device to generate images upon detecting differentdelivery events. For example, upon detection of a drop-off, an image ofthe item being dropped off may be generated. Similarly, upon a movementor a pick-up, corresponding images may be generated. Such images may bestored locally at the delivery management device 244 and/or transmittedto the computer system 220 and/or the user device 260. For example, theimages may be added to the notifications.

When optical sensors are used, various image recognition techniques,such as facial recognition techniques, may be optionally implemented.Such techniques may be implemented at the delivery management device 244and/or the computer system 220. An image may be analyzed using facialrecognition techniques to detect a success or a failure of a deliveryevent. For example, the delivery management device 244 may have accessto an image of the user from, for example, the user account. Uponpick-up, the delivery management device 244 may analyze thecorresponding image, detect a face of the individual who picked up theitem, and compare the detected face to the known image of the user. Ifthere is a match, the delivery management device 244 may determine thatthe pick-up may have been successful; otherwise, failure may bedetermined. A notification about the success or the failure may beprovided to the user device 260.

As such, the passive device 210 may be used in conjunction with thedelivery management device 244 and/or the delivery device 230 tofacilitate various notifications to the user device 260. Thesenotifications may span the entire delivery process, such as from thestart of the delivery to the pick-up of the item at the destination 240,and may include information about different delivery events.

In addition to interfacing with the computer system 220, the deliverydevice 230, and/or the user device 260, the delivery management device244 may interface with other nodes of the local area network 242 of thedestination 240. These nodes may include various automation devices,e.g., connected or smart devices or appliances, installed at thedestination 240. For example, the nodes may include a smart switch forturning on and off a light, a smart switch for turning on and off anoven, or other automation device. Upon a delivery event, the deliverymanagement device 244 may indicate the delivery event to the one or moreof the automation devices over the local area network 242. In response,an automation device may initiate an action at the destination 240. Theaction may be predefined by the user. For instance, upon drop-off of afrozen entrée, the delivery management device 244 may identify the item(e.g., the frozen entrée) based on the order and access instructions forpreparing the item (e.g., cooking temperature) from a remote computingresource (e.g., from the computer system 220). The delivery managementdevice 244 may inform a smart switch about the drop-off and some of theinstructions for preparing the item (e.g., the cooking temperature). Inturn, the switch may turn on an oven and set the bake temperatureaccording to the information received from the delivery managementdevice 244.

Generally, the delivery process may include multiple phases. At eachphase, interactions between different components may be possible,thereby resulting in different notifications. FIG. 3 provides anillustrative table summarizing the phases, the interacting components,and the resulting notifications. Some of the interactions or informationthereof may be tracked by a computer system and used to generate thenotifications by the computer system and/or by one or more of theinteracting components. As such, the computer system may be involved inthe various phases but is not shown in FIG. 3 in the interest of clarityof explanation.

As illustrated, the delivery process may include four phases 310:preparation 312, in-route 314, drop-off 316, and pick-up 318. Otherphases and/or combination of phases may also exist. At each phase, oneor more interacting components 320 may be involved. The interactions mayresult in one or more end user notifications 330 and/or one or moredelivery device notifications 340. The end user notifications 330 may beprovided to a user device, such as the user device 260 of FIG. 2. Incomparison, the delivery notifications 340 may be provided to a deliverydevice, such as the delivery device 230 of FIG. 2.

In the preparation phase 312, an order for an item may have beenreceived and may be processed to prepare for the delivery. The computersystem may provide instructions for including a passive device with theorder or item. As such, the interacting components 320 may include thepassive device. The end user notifications 330 and the delivery devicenotification 340 may describe that the order may be under processing.

In the in-route phase 314, the delivery may have started but a drop-offmay not have occurred yet. For example, the item may have been loadedonto a delivery vehicle and the delivery vehicle may be in-route to adestination. As such, the interacting components 320 may include thepassive device and the delivery device. As a result, the end usernotifications 330 may indicate a start of the delivery and provide thelocation of the item while in-route. In comparison, the delivery devicenotifications 340 may include delivery instructions.

In the drop-off phase 316, the delivery device and the passive devicemay have arrived to the destination. Resulting interactions with adelivery management device may have resulted in a drop-off. As such, theinteracting components 320 may include the passive device, the deliverydevice, and the delivery management device. The end user notifications330 may indicate a completion and a time of drop-off. The end usernotifications 330 may also describe a location of the item (e.g., thedrop-off location) and any environmental conditions (including relevantrecommendations). In comparison, the delivery device notifications 340may include delivery instructions, such as the location of the deliverymanagement device and any authorization therefrom for the drop-off. Thedelivery device notifications 340 may also include information about avirtual handoff.

In the pick-up phase 318, the delivery device may have departed thedestination. However, additional interactions may occur between thepassive device, the delivery management device, and/or the user deviceuntil a pick-up may have been detected. As such, the interactingcomponents 320 may include the passive device, the delivery managementdevice, and the user device. As a result, the end user notifications 330may indicate a movement, a lack of movement (e.g., based on an elapsedtime period), and/or a pick-up of the item. The end user notifications330 may also describe a location of the item (e.g., the drop-offlocation) and any environmental conditions (including relevantrecommendations). In comparison, the delivery device notifications 340may similarly provide information about the movement, pick-up, and/orenvironmental conditions. Interactions and notifications with otherdevices may also exist. For example, the delivery management device mayinform an automated device located at the destination of the drop-off,movement, and/or pick-up of the item.

As such, throughout the different phases of the delivery, meaningfulnotifications may be provided to the respective devices. As a result,the various involved parties may have access to the latest and mostup-to-date information about the item (or the delivery thereof). Inaddition, because the notifications may be tailored based on theinteractions, a sufficient or desired amount of notifications may begenerated and transmitted, which may optimize the usage of the variouscomputing resources.

FIG. 4 illustrates another embodiment for providing notifications. Inthis embodiment, an active device may be used instead of a passivedevice. Being active may reflect an implementation where the device maybe self-powered and capable of performing various operations based on alocal processor and memory. For example, an active device may representa computing device with a suitable form factor for attachment to aholder of the item and for usage in the delivery of the item. By usingan active device, much of the functionalities of a delivery managementdevice may be pushed to the active device. Depending on theimplementation of the active device, the delivery management device maynot be even needed.

As illustrated in FIG. 4, a user device 410 may interact with acomputing system 420 of an electronic marketplace over a network 430 toorder an item for delivery to a destination 440. Notifications about theitem, the order, and/or the delivery may be provided to the user device410. As part of the delivery, a holder 450 may hold the item. An activedevice 452 may be attached to the holder. The active device 452 mayinteract with a delivery device 460 and a local area network 442 (or acomputing node of such network). The interactions may result in thenotifications to the user device 410.

In an example, the active device 452 may include a processor, memory, awireless or wired interface, and a power source to facilitate thenotifications. For instance, the active device 452 may include an active802.11 RFID tag. Other configurations of the active device 452 may beused. For instance, the active device 452 may include additionalhardware and/or software components, such as a GPS receiver, varioussensors, and/or a delivery management module. In addition, the activedevice 452 may include an interface for attaching to the holder 450,such as an interface that may use adhesive surfaces, magnets, hook andloop fasteners, and/or other attachment means.

The local area network 442 may communicatively connect various computingnodes located at the destination 440 (e.g., inside or within ageographical fence of the destination 440). The local area network 442may also be connected to the network 430 such that a communication pathmay exist between the computing nodes and the computer system 420, theuser device 410, and/or the delivery device 460. These computing nodesmay include, for example, an access point, a router, an intermediarycomputing device capable of tethering external computing devices (e.g.,the active device 452) to the local area network 442, automated devices,imaging devices, and/or other computing resources.

To facilitate the interactions and thereby provide notifications,various tokens may be used between the active device 452, the local areanetwork 442 (e.g. a computing node of the local area network 442), andthe delivery device 460. Generally, a token may represent a secret thatmay be shared between computing devices to facilitate communicationsbetween the computing devices. The token may be revocable to facilitatethe management of the communications. For example, the token may expireafter a period of time or after a number of usages (e.g., one usage). Assuch, once the delivery may be complete, the token may no longer beusable.

In an example, upon the order for the item, a token may be generated anddistributed to the proper computing devices. For example, the token maybe generated by the computer system 420, the user device 410, and/or acomputing node of the local area network 442. The same token, portionsof the token, or a different token may be sent to the active device 452,the local area network 442 (e.g., the computing node thereof), and/orthe delivery device 460. As shown in FIG. 4, a received token may bestored at the local area network 442 as a token 444, at the activedevice 452 as a token 454, and at the delivery device 460 as a token462. The tokens 444, 454, 462 may be copies of the same token, differenttokens, or portions of a same token.

In operation, the tokens 444 and 454 may be generated and distributedupon an order of an item. The token 462 may be similarly generated anddistributed or may be a predefined token independently of the order. Thetokens may be used to determine proximities between the differentcomponents. Notifications, including ones about delivery events, may begenerated based on the proximities. In addition, delivery instructionsmay be provided from the computer system 420 and/or the user device 410to the active device 452, the delivery device 460, and/or a computingnode of the local area network 442 over the network 430. The deliveryinstructions may be similar to the ones described in connection withFIG. 2.

Upon a start of the delivery, the delivery device 460 may interact withthe active device (e.g., read the RFID tag or exchange information overa communication link). The tokens 454 and 462 may, but need not, be usedto authorize the start of the delivery. If the delivery device 460 doesnot have the delivery instructions, such instructions may be providedfrom the active device 452. In addition, a notification about the startof the delivery may be generated and provided to the user device 410. Inan example, the active device 452 and/or the delivery device 460 maygenerate the notification. In another example, the communication betweenthe active device 452 and the delivery device 460 may trigger thecomputer system 420 to generate the notification. Once generated, thenotification may be sent to the user device 410 over the network 430. Inan example, the computer system 420 may send the notification. Inanother example, the active device 452 and/or the delivery device 460may send the notification independently of the computer system 420.

In route, the communication between the active device 452 and thedelivery device 460 may be retained. For example, one or both of thedevices 452 and 460 may ping each other and, accordingly, determine thatthe communication may still exist and that the two devices may be inproximity to each other. Based on this proximity, a notification to theuser device 410 may be provided. The notification may indicate that theitem may be in route and may show the geographical location of the itembased on the location of the active device 452, the delivery device 460,and/or delivery vehicle. The active device 452, the delivery device 460,and/or the computer system 420 may generate and send the notification tothe user device 410 over the network 430.

Upon arrival to the destination 440 (e.g., upon entry to a geographicalfence of the destination 440), proximities between the local areanetwork 442, the active device 452, and/or the delivery device 460 maybe determined. These proximities may be used to authorize a drop-off,provide delivery instructions, detect a drop-off, detect a lack of adrop-off, and/or complete a virtual handoff. The proximities may bebased on interactions between the local area network 442 (or a computingnode thereof), the active device 452, and/or the delivery device 460.These interactions may be facilitated through communications that mayuse the tokens 444, 454, and 462. Upon occurrence of any of these events(e.g., authorization, drop-off, and/or virtual handoff), informationabout the event may be provided from the local area network 442 (or thecomputing node thereof), the active device 452, and/or the deliverydevice 460 to the computing system 420. A corresponding notification mayalso be sent to the user device 410 by the computer system 420 orindependently of the computer system 420 (e.g., by the local areanetwork 442 (or the computing node thereof), the active device 452,and/or the delivery device 460).

In an example, the active device 452 and the local area network 442 (ora computing node thereof) may establish a communication link based onthe tokens 454 and 444. Similarly, the delivery device 460 and/or thelocal area network 442 (or the computing node thereof) may establish acommunication link based on the tokens 462 and 444. In addition, acommunication link may exist or be established between the active device452 and the delivery device 460. This communication link may, but neednot, use the tokens 454 and 462. Upon establishing communication withthe local area network 442, the active device 452 may determine whethera drop-off may occur based on pre-stored delivery instructions or anyother instructions received over the communication link (e.g., whetherthe correct item is in the delivery, the time of the delivery, anyspecial drop-off instructions, etc.). If so, the active device 452 mayauthorize the drop-off for the delivery device 460 and provide relevantdelivery instructions. Otherwise, the drop-off may be rejected.

The detection of a drop-off may use various proximity orinteraction-based rules. In an example, if the local area network 442(or the computing node thereof) and the active device 452 maintaincommunication for a predefined period of time (e.g., five minutes), thedrop-off may be determined. In another example, a user interface (orsome other interface) of the delivery device 460 may receive anindication of the drop-off (from the operator or from the deliveryvehicle) and may send this indication to the local area network 442 (orthe computing node thereof) and/or the active device 452. In yet anotherexample, the rules may specify that the drop-off may have occurred ifthe communication between the local area network 442 (or the computingnode thereof) and the active device 452 is maintained while thecommunication of the local area network 442 (or the computing nodethereof) and/or the active device 452 with the delivery device 460 isterminated.

The detection of a lack of a drop-off may also use the variousproximities. In an example, upon a proximity of the local area network442 (or the computing node thereof) and the delivery device 460 but alack of proximity between the local area network 442 (or the computingnode thereof) and the active device 452, the local area network 442 (orthe computing node thereof) may detect that no drop-off has occurred.Accordingly, a notification about the lack of drop-off may be generated.In addition, in this case the local area network 442 (or the computingnode thereof) may perform an automatic action. Such an action may bedefined in the delivery instructions. For example, the local areanetwork 442 (or the computing node thereof) may re-order the item withan expedited ship method, reschedule a delivery, or request a refund.

The virtual handoff may be detected based on interactions of the activedevice 452 and/or the local area network 442 (or the computing nodethereof) with the delivery device 460. For example, the delivery device460 may request a virtual signature from the active device 452 and/orthe local area network 442 (or the computing node thereof). Upondetecting the drop-off, the active device 452 and/or the local areanetwork 442 (or the computing node thereof) may respond with the virtualsignature. In another example, upon detecting the drop-off and once thecommunications with the delivery device 460 are terminated (e.g.,because of physical distance), the delivery device 460, the activedevice 452, and/or the local area network 442 (or the computing nodethereof) may determine that the virtual handoff may have occurred.

Subsequent to the delivery device 460 departing from the destination 440and/or the termination of any communication with the active device 452and/or the local area network 442 (or the computing node thereof),notifications about movement, lack of movement (e.g., based on anelapsed time period as described in connection with FIG. 2), relevantenvironmental conditions, and/or a pick-up of the item may be provided.Upon occurrence of any of these events (e.g., movement, an environmentalcondition, pick-up), information about the event may be provided fromthe local area network 442 (or the computing node thereof) and/or theactive device 452 to the computing system 420. A correspondingnotification may also be sent to the user device 410 by the computersystem 420 or independently of the computer system 420 (e.g., by thelocal area network 442 (or the computing node thereof) and/or the activedevice 452).

Various techniques may be used to detect a movement of the item. In anexample, RF ranging may be used. For example, the active device 452and/or the local area network 442 (or the computing node thereof) mayestimate a proximity (e.g., a distance) based on the communicationbetween the two and the strength of the RF signal. If that proximitychanges, the movement may be detected. In addition, if the communicationterminates, the active device 452 and/or the local area network 442 (orthe computing node thereof) may detect that the item may have departedfrom the geographical fence of the destination 440 (unless a pick-up mayhave occurred). In yet another example, the movement may be determinedon GPS location of the active device 452. For instance, if the activedevice 452 includes a GPS receiver and the corresponding GPS dataindicates a location change, the movement may be detected.

Similarly, various techniques may be used to detect an environmentalcondition that may impact the item. In an example, the active device 452may include one or more environmental sensors (e.g., rain sensors).These sensors may detect the environmental condition. In anotherexample, the local area network 442 (or the computing node thereof) orthe computer system 420 may access environmental information about thedestination 440 from a web site over the network 430 to determine theenvironmental condition. If this condition is detected prior to apick-up, the computer system 420, the active device 452, and/or thelocal area network 442 may provide a recommendation to the user device410 related to the environmental condition (e.g., a recommendation for apick-up within a time frame, to move the item to a covered area, etc.).

Various techniques may also be used to detect a pick-up. In one example,an indication of the pick-up may be received at a user interface of theactive device 452 (if the device includes such an interface) or remotelyfrom the user device 410. In another example, the pick-up may bedetermined based on the proximity of the user device 410 to the activedevice 452 and/or the local area network 442 (or the computing nodethereof). For instance, the computer system 420 may detect the proximitybased on the respective GPS locations. Additionally or alternatively,the active device 452 and/or the local area network 442 (or thecomputing node thereof) may receive the GPS location of the user device410 from the computer system 420 or from the user device 410independently of the computer system 420. Based on the proximity and amovement of the item, the pick-up may be detected.

The destination 440 may also include various optical sensors. Theoptical sensors may form an imaging device. The local area network 442(or a computing node thereof) and/or the computer system 420 may triggerthe imaging device to generate images upon detecting different deliveryevents including drop-off, movement, lack of movement, and/or pick-up.Such images may be stored locally at the local area network 442 and/ortransmitted to the computer system 420 and/or the user device 410. Forexample, the images may be added to the notifications.

When optical sensors are used, various image recognition techniques,such as facial recognition techniques, may be optionally implemented.Such techniques may be implemented at local area network 442 (or acomputing node thereof) and/or the computer system 420. An image may beanalyzed using facial recognition techniques to detect a success or afailure of a delivery event. For example, the computer system 420 mayhave access to an image of the user from, for example, the user account.Upon pick-up, the computer system 420 may analyze the correspondingimage, detect a face of the individual who picked up the item, andcompare the detected face to the known image of the user. If there is amatch, the computer system 420 may determine that the pick-up may havebeen successful; otherwise, failure may be determined. A notificationabout the success or the failure may be provided to the user device 410.

As such, the active device 452 may be used in conjunction with the localarea network 442 and/or the delivery device 460 to facilitate variousnotifications to the user device 410. These notifications may span theentire delivery process, such as from the start of the delivery to thepick-up of the item at the destination 440.

In addition to interfacing with the local area network 442, the computersystem 420, the delivery device 460, and/or the user device 410, theactive device 452 may interact with other nodes of the local areanetwork 442 through the local area network 442. These nodes may includevarious automation devices installed at the destination 440. Forexample, the nodes may include a smart switch for turning on and off alight, a smart switch for turning on and off an oven, or otherautomation device. Upon a delivery event, the active device 452 (or acomputing node of the local area network 442) may indicate the deliveryevent to the one or more of the automation devices over the local areanetwork 442. In response, an automation device may initiate an action atthe destination 440, such as for instance turning on an oven based on adrop-off of a frozen entrée.

FIG. 5 provides an illustrative table summarizing different phases,interacting components, and the resulting notifications when an activedevice is used. Some of the interactions or information thereof may betracked by a computer system and used to generate the notifications bythe computer system and/or by one or more of the interacting components.As such, the computer system may be involved in the various phases butis not shown in FIG. 5 in the interest of clarity of explanation.

As illustrated, the delivery process may include four phases 510:preparation 512, in-route 514, drop-off 516, and pick-up 518. Otherphases and/or combination of phases may also exist. At each phase, oneor more interacting components 520 may be involved. The interactions mayresult in one or more end user notifications 530 and one or moredelivery device notifications 540. The end user notifications 530 may beprovided to a user device, such as the user device 410 of FIG. 4. Incomparison, the delivery notifications 540 may be provided to a deliverydevice, such as the delivery device 460 of FIG. 4.

In the preparation phase 512, an order for an item may have beenreceived and may be processed to prepare for the delivery. The computersystem may provide instructions for including an active device with theorder or item. These instructions may relate to the delivery and mayinclude a token usable by the active device to access a local areanetwork at the destination. As such, the interacting components 520 mayinclude the active device, and the end user notifications 430 and thedelivery device notifications 440 may describe that the order may beunder processing. In this phase, the same or a different token may beprovided to the delivery device for accessing the local area network 442and/or the active device 452.

In the in-route phase 514, the delivery may have started but a drop-offmay not have occurred yet. The interacting components 520 may includethe active device and the delivery device. The end user notifications530 may indicate a start of the delivery and provide the location of theitem while in-route. In comparison, the delivery device notifications540 may include delivery instructions. If no token may have beenprovided to the delivery device in the preparation phase 512, such atoken may be provided from the active device or the computer system tothe delivery device in the in-route phase 514.

In the drop-off phase 516, the delivery device and the active device mayhave arrived to the destination. Resulting interactions with the localarea network (or a computing node thereof) may have resulted in adrop-off. As such, the interacting components 520 may include the activedevice, the delivery device, and the local area network (or thecomputing node thereof). The end user notifications 530 may indicate acompletion and a time of drop-off. The end user notifications 530 mayalso describe a location of the item (e.g., the drop-off location basedon a GPS receiver of the active device if one is used or based on userinput at the delivery device) and any environmental conditions(including relevant recommendations). In comparison, the delivery devicenotifications 540 may include delivery instructions, such as thelocation of the delivery management device and any authorizationtherefrom for the drop-off. The delivery device notifications 540 mayalso include information about a virtual handoff

In the pick-up phase 518, the delivery device may have departed thedestination. However, interactions may occur between the active device,the local area network (or the computing node thereof), and/or the userdevice until a pick-up may have been detected. As such, the interactingcomponents 520 may include the active device, the local area network (orthe computing node), and the user device. The end user notifications 530may indicate a movement, a lack of movement (e.g., based on an elapsedtime period), and/or a pick-up of the item. The end user notifications530 may also describe a location of the item (e.g., the drop-offlocation) and any environmental conditions (including relevantrecommendations). In comparison, the delivery device notifications 540may similarly provide information about the movement, pick-up, and/orenvironmental conditions. Interactions and notifications with otherdevices may also exist. For example, the active device and/or the localarea network (or the computing node thereof) may inform an automateddevice located at the destination of the drop-off, movement, and/orpick-up of the item.

Turning to FIGS. 6-10 those figures illustrate example flows formanaging notifications. FIG. 6 illustrates an example high level flowfor generating and transmitting notifications. FIGS. 7 and 8 illustrateexample flows that a computer system and a delivery management device,respectively, may implement to manage notifications in a computingenvironment that may include a passive device. In comparison, FIGS. 9and 10 illustrate example flows that a computer system and an activedevice, respectively, may implement to manage notifications in acomputing environment that may include the active device. Some of theoperations of the example flows of FIGS. 6-10 may be similar. Suchsimilarities are not repeated herein in the interest of clarity ofexplanation.

Further, in the illustrative operations, some of the operations orfunctions may be embodied in, and fully or partially automated by,modules executed by one or more processors. Also, while the operationsare illustrated in a particular order, it should be understood that noparticular order is necessary and that one or more operations may beomitted, skipped, and/or reordered.

The example flow of FIG. 6 may start at operation 602, where an orderfor an item may be received. For example, a user may operate a userdevice to access an electronic marketplace offering the item over anetwork. A computer system facilitating functionalities of theelectronic marketplace may receive an order for the item from the userdevice. The computer system may also receive a description, such as anaddress, of a destination for a delivery of the item.

At operation 604, the delivery of the item may be prepared. For example,the computer system may provide instructions about the delivery.Depending on the implementations, the instructions may be used toconfigure a passive device and/or an active device that may be attachedto a holder holding the item for the delivery. Configuring the passivedevice may include storing information about the order, the item, thedestination, and/or the delivery instructions in the passive device, orin association with an identifier stored in the passive device. Forexample, a passive RFID tag encoding the information may be printed.Configuring the active device may include storing similar information atthe active device, or in association with an identifier stored in theactive device. In addition, a token for accessing a local area networkassociated with the destination may be stored in the active device, orin association with an identifier stored in the active device. Anexample active device may include an active 802.11 RFID tag.

At operation 606, a notification about a start of the delivery may beprovided to the user device. For example, a delivery device may interactwith the passive device and/or active device. The delivery device may beassociated with a delivery vehicle. The interaction may depend on theimplementation of such devices. For instance, RF-based communicationsmay be used. Upon an interaction, the computer system may receive anindication of the interaction from the delivery device and/or the activedevice over a network. This indication may represent the start of thedelivery. In addition, the computer system, the active device, and/orthe delivery device may send the notification to the user device basedon the interaction.

At operation 608, location data may be provided to the user devicethroughout the delivery up to arrival to the destination. For example,the passive device, the active device, the delivery device, and/or thedelivery vehicle may include a location positioning device(s), such as aGPS receiver(s). The local positioning device(s) may provide thelocation data to the computer system. In turn, the computer system mayfacilitate access to the location data by the user device.

At operation 610, a notification about a drop-off of the item at thedestination may be sent to the user device. If the passive device isused, a delivery management device may be located at the destination.Interactions of the delivery management device with the passive deviceand/or the delivery device may result in detecting the drop-off. Incomparison, if the active device is used, a computing node of a localarea network at the destination may interact with the active deviceand/or the delivery device. The interactions may be used to determinethe drop-off. In both cases, the computer system may receive anindication of the drop-off from the delivery management device, thedelivery device, the computing node of the local area network, and/orthe active device. In addition, the computer system, the deliverymanagement device, the delivery device, the computing node of the localarea network, and/or the active device may send the correspondingnotification to the user device.

At operation 612, a notification about movement of the item at thedestination may be sent to the user device. If the passive device isused, the delivery management device may determine that the proximitybetween the delivery management device and the passive device may havechanged. This change may correspond to the movement. The proximitydetermination may use different techniques, such as RF ranging (using anRF transceiver of the delivery management device), optical ranging(using an optical sensor of the delivery management device), and/orsensing weight and/or pressure changes (with weight and/or pressuresensors of the delivery management device). If the active device isused, the computing node of the local area network may determine thatthe proximity between the computing node and the active device may havechanged. This change may correspond to the movement. The proximitydetermination may use different techniques, such as RF ranging (using anRF transceiver of the computing node), and/or using position location(e.g., GPS data of the active device). The computer system may receivean indication of the movement from the delivery management device, thedelivery device, the computing node of the local area network, and/orthe active device. In addition, the computer system, the deliverymanagement device, the delivery device, the computing node of the localarea network, and/or the active device may send the correspondingnotification to the user device.

At operation 614, a notification about a pick-up of the item at thedestination may be sent to the user device. Different techniques may beused to determine the pick-up. In an example, proximities may be used.For instance, proximity between the user device and the deliverymanagement device and/or the computing node of the local area networkmay be determined (e.g., based on GPS data, RF ranging, etc.). Thisproximity may be compared to the proximity of the user device, thedelivery management device, and/or the computing node of the local areanetwork to the passive device and/or active device. The pick-up may bedetermined based on the comparison. For example, if the comparisonindicates that the user device is in proximate location to the passivedevice and/or active device, the pick-up may have occurred. The computersystem may receive an indication of the pick-up from the deliverymanagement device, the delivery device, the computing node of the localarea network, and/or the active device. In addition, the computersystem, the delivery management device, the delivery device, thecomputing node of the local area network, and/or the active device maysend the corresponding notification to the user device.

Turning to FIG. 7, the figure illustrates an example flow that thecomputer system may implement to manage the notifications when thepassive device is used. The example flow may start at operation 702,where the computer system may provide instructions related to thepassive device for the delivery of the item. The instructions may beused to, for instance, store the information about the delivery at thepassive device, or in association with an identifier stored in thepassive device. If a passive RFID tag is used, the instructions may beused to print such a tag.

At operation 704, the computer system may receive an indication of aninteraction between the passive device and the delivery device. Forexample, the delivery device may read, scan, or radiate with RF signalsthe passive device and may accordingly transmit the indication to thecomputer system. At operation 706, the computer system may determine astart of the delivery based on the received indication. In addition, thecomputer system may transmit a notification about the start to the userdevice.

At operation 708, the computer system may provide delivery instructionsto the delivery management device. Similar instructions may also beprovided to the delivery device. In an example, upon the order of theitem, the user device may also specify particular instructions about thedelivery of the item (e.g., specific location at the destination,delivery time, requested signatures, etc.). In response, the computersystem may generate and send the delivery instructions to the deliverymanagement device and/or the delivery device.

At operation 710, the computer system may receive an indication of aninteraction between the delivery management device and the passivedevice. For example, the delivery management device may send anindication, to the computer system, that the passive device may be inproximity of the delivery management device. In addition, the computersystem may receive a similar indication from the delivery device (or thedelivery management device) about a proximity to the delivery managementdevice (or the delivery device).

At operation 712, the computer system may determine that a drop-off mayhave occurred at the destination. This determination may be based on oneor more of the received indications. For example, the computer systemmay determine that a potential drop-off may have occurred based on theproximity of the delivery management device and the passive device. Thecomputer system may confirm this potential drop-off using varioustechniques. For example, after a predefined period of time, if thatproximity is maintained (e.g., based on another indication received fromthe delivery management device), the confirmation may be made. Inanother example, the confirmation may be made based on the indication ofthe proximity of the delivery device and the delivery management device.In yet another example, the computer system may receive the indicationsof proximities between the delivery management device, the deliverydevice, and the passive device. If, after a predefined period of time,the delivery device is no longer located in proximity of the deliverymanagement device, the confirmation may be made. The computer system mayaccordingly send a notification about the drop-off to the user device.

At operation 714, the computer system may receive a change to theproximity between the passive device and the delivery management device.For example, the delivery management device may detect the change andsend an indication of the change to the computer system. At operation716, the computer system may determine movement of the item based on thechange. The computer system may accordingly send a notification aboutthe movement to the user device.

At operation 718, the computer system may determine a pick-up of theitem. For example, the computer system may receive an indication fromthe user device of the pick-up. In another example, proximities of thedelivery management device, the passive device, and the user device maybe used to detect the pick-up. For example, the computer system mayaccess the position location (e.g., GPS data) of the user device and thedelivery management device. If the two devices may be proximate to eachother, the computer system may access (e.g., request and receive orautomatically receive) an indication from the delivery management deviceof movement of the item. The computer system may detect the pick-upbased on such proximities and the movement.

Turning to FIG. 8, the figure illustrates an example flow that thedelivery management device may implement to manage the notificationswhen the passive device is used. The example flow may start at operation802, where the delivery management device may receive deliveryinstructions associated with the order of the item. The deliveryinstructions may be received from the computer system and/or the userdevice and may provide information about the order. For example, theinformation may include a unique identifier associated with the order.

At operation 804, the delivery management device may determine aproximity to the passive device. This proximity may be determined basedon interactions with the passive device and/or the delivery device. Theinteraction may include receiving information about the order, e.g.,from the passive device, or based on information stored in associationwith an identifier in the passive device.

At operation 806, the delivery management device may authorize adrop-off of the item. For example, the delivery management device maycompare the information received from the passive device and/or thedelivery device to the information received from the computer systemand/or user device. If an acceptable match is found (e.g., the uniqueidentifier associated with the order is the same), the drop-off may beauthorized. The delivery instructions may also include, for instance, adelivery time frame and/or environmental conditions (e.g., drop-off tooccur when there is no rain). The delivery management device may furtherauthorize the drop-off based on the delivery time frame and/or theenvironmental conditions. Once authorized, the delivery managementdevice may send an indication of the authorization to the computersystem and/or the delivery device. In addition, the delivery managementdevice and/or the computer system may send a corresponding notificationto the user device.

At operation 808, the delivery management device may provide a portionof the delivery instructions to the delivery device. For example, thedelivery instructions may include a specific location to drop-off theitem at the location. As such, the delivery management device mayidentify this location to the delivery device.

At operation 810, the delivery management device may determine acompletion of the drop-off. This determination may be made based onproximity of the delivery management device to the passive device and/orthe delivery device. For example, if the passive device remains inproximity of the delivery management device for a predefined period oftime, the completion of the drop-off may be detected. In anotherexample, if the delivery device is no longer in proximity of thedelivery management device, the completion of the drop-off may bedetected.

At operation 812, the delivery management device may provide informationabout the completion of the drop-off to the computer system, thedelivery device and/or the user device. For example, the deliverymanagement device may send an indication of the completion of thedrop-off to the computer system and/or the delivery device. In addition,the delivery management device and/or the computer system may send acorresponding notification to the user device.

At operation 814, the delivery management device may determine a changeto the proximity between the delivery management device and the passivedevice. At operation 816, the delivery management device may determinemovement of the item based on the change to the proximity. The deliverymanagement device may send an indication of the movement to the computersystem. In addition, the delivery management device and/or the computersystem may send a corresponding notification to the user device.

At operation 818, the delivery management device may determine a pick-upof the item. The pick-up may be determined based on the proximity (orlack thereof) to the passive device. For instance, if the passive deviceis no longer at a location proximate to the delivery management device,the pick-up may be determined. In addition, the pick-up may bedetermined based on the proximity to the user device. For example, thedelivery management device may determine the location of the user device(e.g., based on GPS data of the user device, where the GPS data may bereceived from the user device or the computer system). If the userdevice and the passive device are proximate to the delivery managementdevice at one point in time after which both devices are no longerproximate to the delivery management device, the pick-up may bedetected. The delivery management device may send an indication of thepick-up to the computer system. In addition, the delivery managementdevice and/or the computer system may send a corresponding notificationto the user device.

Turning to FIG. 9, the figure illustrates an example flow that thecomputer system may implement to manage the notifications when theactive device is used. The example flow may start at operation 902,where the computer system may provide a token for storage at the activedevice. The token may be generated by the computer system, the userdevice, and/or a computing node of the local area network of thedestination based on the order of the item.

At operation 904, the computer system may receive an indication of aninteraction between the active device and the delivery device. Forexample, the delivery device may read, scan, or establish datacommunication with the active tag and may accordingly transmit theindication to the computer system. At operation 906, the computer systemmay determine a start of the delivery based on the received indication.In addition, the computer system may transmit a notification about thestart to the user device.

At operation 908, the computer system may provide delivery instructionsto the delivery device. At operation 910, the computer system mayreceive an indication from the computing node of the local area networkabout the communication with the active device. The communication may bebased on the token. For example, the computing node may receive thetoken from the active device and, accordingly, authenticate the activedevice. The computing node may send an indication of the communicationto the computer system. In addition, the computer system may receive anindication of a communication between the delivery device and thecomputing node. This communication may also be based on a same or adifferent token. The indication of the communication may be receivedfrom the delivery device and/or the computing node.

At operation 912, the computer system may determine that a drop-off mayhave occurred at the destination. This determination may be based on oneor more of the received indications. For example, the computer systemmay determine that a potential drop-off may have occurred based on thecommunication of the computing node and the active device. The computersystem may confirm this potential drop-off using various techniques. Forexample, the drop-off may be confirmed based on the communicationbetween the delivery device and the computing node, or based on thetermination of such a communication (which may be received in anotherindication from the delivery device and/or the computing node). Inanother example, the drop-off may be determined based on the proximityof the active device to the destination. For instance, the computersystem may receive the location information (e.g., GPS data) of theactive device and may compare the location information to the one of thedestination. If the active device remains within a geographical fence ofthe destination for a predefined period of time, the drop-off may haveoccurred. In yet another example, the drop-off may be determined basedon the proximity of the delivery device to the destination. Forinstance, the computer system may receive the location information(e.g., GPS data) of the delivery device and may compare the locationinformation to the one of the destination. If the delivery device entersand then leaves the geographical fence while the communication betweenthe computing node and the active device persists, the drop-off may becomplete.

At operation 914, the computer system may receive a change to theproximity between the active device and the delivery management device.For example, the computer system may receive the location information(e.g., GPS data) of the active device and may compare the locationinformation to the one of the destination. If there is a change in thelocation information, that change may correspond to the proximitychange. At operation 916, the computer system may determine movement ofthe item based on the change. The computer system may accordingly send anotification about the movement to the user device.

At operation 918, the computer system may determine a pick-up of theitem. For example, the computer system may receive an indication fromthe user device of the pick-up. In another example, proximities of thecomputing node, the active device, and the user device may be used todetect the pick-up. For example, the computer system may access thelocation information (e.g., GPS data) of the computing node, the activedevice, and the user device to determine the proximities and accordinglydetect the pick-up.

Turning to FIG. 10, the figure illustrates an example flow that theactive device may implement to manage the notifications. The exampleflow may start at operation 1002, where the active device may store thetoken associated with the item delivery. The token may be received fromthe computer system, a computing node of the local area network of thedestination, and/or the user device.

At operation 1004, the active device may establish communication withthe delivery device. At operation 1006, the active device may cause anindication of the start of the delivery. For example, the communicationmay cause the delivery device and/or the active device to send theindication to the computer system. In addition, the computer system, thedelivery device, and/or the active device may send a correspondingnotification to the user device.

At operation 1008, the active device may establish communication withthe computing node of the local area network. This communication may beestablished based on an authentication of the active device using thetoken.

At operation 1010, the active device may cause a determination of adrop-off of the item. The drop-off may be determined based on proximityof the active device to the computing node and/or the delivery device.Based on this proximity, the active device, the computing node, thedelivery device, and/or the computer system may determine that thedrop-off may have occurred. A corresponding notification may be sent tothe user device and/or the delivery device. In an example, the activedevice may provide its location information (e.g., GPS data) to thecomputer system and/or the computing node or may receive the locationinformation of the destination. Based on a comparison of the locationinformation, the proximity may be determined. In another example, thecomputing node and/or the active device may use RF ranging to detect theproximity. This proximity may be used with other factors to determine acompletion of the drop-off. For example, if the active device and thecomputing node remain in proximity for a pre-defined period of time, thedrop-off may be complete. In another example, if the delivery device isno longer in proximity to the active device, the drop-off may becomplete.

At operation 1012, the active device may cause a determination of amovement of the item. The movement may be determined based on proximityof the active device to the computing node. Based on this proximity, theactive device, the computing node, and/or the computer system maydetermine that the movement may have occurred. A correspondingnotification may be sent to the user device. In an example, a change inthe location information of the active device relative to destinationmay indicate the movement of the item. In another example, RF rangingmay be applied based on the communication between the active device andthe computing node. The RF ranging may indicate a change in a distancerange between the active device and the computing node. This change maycorrespond to the movement of the item.

At operation 1014, the active device may cause a determination of apick-up of the item. The pick-up may be determined based on proximitybetween the active device, the computing node, and/or the user device.Based on this proximity, the active device, the computing node, and/orthe computer system may determine that the pick-up may have occurred. Acorresponding notification may be sent to the user device. In anexample, if the user device moves to a location proximate to the activedevice, the pick-up may be determined.

Turning to FIG. 11, that figure illustrates an example end-to-endcomputing environment for managing notifications in connection with anelectronic marketplace. In this example, a service provider mayimplement a notification manager to manage the notifications. Thenotifications may relate to items available from the electronicmarketplace. The items may be listed for offering by a seller 1110and/or the service provider and may be available for ordering by acustomer 1160.

In a basic configuration, the seller 1110 may utilize a seller device1112 to access local applications, a web service application 1120, aseller account accessible through the web service application 1120, aweb site or any other network-based resources via one or more networks1180. In some aspects, the web service application 1120, the web site,and/or the seller account may be hosted, managed, and/or otherwiseprovided by one or more computing resources of the service provider,such as by utilizing one or more service provider devices 1130. Theseller 1110 may use the local applications and/or the web serviceapplication 1120 to interact with the network-based resources of theservice provider and perform seller-related transactions. Thesetransactions may include, for example, offering items for sale.

In some examples, the seller device 1112 may be any type of computingdevices such as, but not limited to, a mobile phone, a smart phone, apersonal digital assistant (PDA), a laptop computer, a thin-clientdevice, a tablet PC, etc. In one illustrative configuration, the sellerdevice 1112 may contain communications connection(s) that allow theseller device 1112 to communicate with a stored database, anothercomputing device or server, seller terminals, and/or other devices onthe networks 1180. The seller device 1112 may also include input/output(I/O) device(s) and/or ports, such as for enabling connection with akeyboard, a mouse, a pen, a voice input device, a touch input device, adisplay, speakers, a printer, etc.

The seller device 1112 may also include at least one or more processingunits (or processor device(s)) 1114 and at least one memory 1116. Theprocessor device(s) 1114 may be implemented as appropriate in hardware,computer-executable instructions, firmware, or combinations thereof.Computer-executable instructions or firmware implementations of theprocessor device(s) 1114 may include computer-executable ormachine-executable instructions written in any suitable programminglanguage to perform the various functions described.

The memory 1116 may store program instructions that are loadable andexecutable on the processor device(s) 1114, as well as data generatedduring the execution of these programs. Depending on the configurationand type of seller device 1112, the memory 1116 may be volatile (such asrandom access memory (RAM)) and/or non-volatile (such as read-onlymemory (ROM), flash memory, etc.). The seller device 1112 may alsoinclude additional storage, which may include removable storage and/ornon-removable storage. The additional storage may include, but is notlimited to, magnetic storage, optical disks, and/or tape storage. Thedisk drives and their associated computer-readable media may providenon-volatile storage of computer-readable instructions, data structures,program modules, and other data for the computing devices. In someimplementations, the memory 1116 may include multiple different types ofmemory, such as static random access memory (SRAM), dynamic randomaccess memory (DRAM), or ROM.

Turning to the contents of the memory 1116 in more detail, the memorymay include an operating system (O/S) 1118 and the one or moreapplication programs or services for implementing the features disclosedherein including the web service application 1120. In some examples, theseller device 1112 may be in communication with the service providerdevices 1130 via the networks 1180, or via other network connections.The networks 1180 may include any one or a combination of many differenttypes of networks, such as cable networks, the Internet, wirelessnetworks, cellular networks, and other private and/or public networks.While the illustrated example represents the seller 1110 accessing theweb service application 1120 over the networks 1180, the describedtechniques may equally apply in instances where the seller 1110interacts with the service provider devices 1130 via the seller device1112 over a landline phone, via a kiosk, or in any other manner. It isalso noted that the described techniques may apply in otherclient/server arrangements (e.g., set-top boxes, etc.), as well as innon-client/server arrangements (e.g., locally stored applications,peer-to-peer systems, etc.).

Similarly, a customer 1160 may utilize customer device 1162 to accesslocal applications, a web service application 1170 (or some other mobileapplication such as a “mobile app” available from an application store),a customer account accessible through the web service application 1170,a web site, or any other network-based resources via the networks 1180.In some aspects, the web service application 1170, the web site, and/orthe user account may be hosted, managed, and/or otherwise provided bythe service provider devices 1130 and may be similar to the web serviceapplication 1120, the web site accessed by the computing device 1112,and/or the seller account, respectively.

The customer 1160 may use the local applications and/or the web serviceapplication 1170 to conduct transactions with the network-basedresources of the service provider. These transactions may include, forexample, browsing for items, viewing items, ordering items, reviewingitems, returning items, receiving notifications, viewing notifications,dismissing notifications, and/or other transactions.

In some examples, the customer device 1162 may be configured similarlyto the seller device 1112 and may include at least one or moreprocessing units (or processor device(s)) 1164 and at least one memory1166. The processor device(s) 1164 may be implemented as appropriate inhardware, computer-executable instructions, firmware, or combinationsthereof similarly to the processor device(s) 1114. Likewise, the memory1166 may also be configured similarly to the memory 1116 and may storeprogram instructions that are loadable and executable on the processordevice(s) 1164, as well as data generated during the execution of theseprograms. For example, the memory 1166 may include an operating system(O/S) 1168 and the one or more application programs or services forimplementing the features disclosed herein including the web serviceapplication 1170.

As described briefly above, the web service applications 1120 and 1170may allow the seller 1110 and customer 1160, respectively, to interactwith the service provider devices 1130 to conduct transactions involvingitems. The service provider devices 1130, perhaps arranged in a clusterof servers or as a server farm, may host the web service applications1120 and 1170. These servers may be configured to host a web site (orcombination of web sites) viewable via the computing devices 1112 and1162. Other server architectures may also be used to host the webservice applications 1120 and 1170. The web service applications 1120and 1170 may be capable of handling requests from many sellers 1110 andcustomers 1160, respectively, and serving, in response, variousinterfaces that may be rendered at the computing devices 1112 and 1162such as, but not limited to, a web site. The web service applications1120 and 1170 may interact with any type of web site that supportsinteraction, including social networking sites, electronic retailers,informational sites, blog sites, search engine sites, news andentertainment sites, and so forth. As discussed above, the describedtechniques may similarly be implemented outside of the web serviceapplications 1120 and 1170, such as with other applications running onthe computing devices 1112 and 1162, respectively.

The service provider devices 1130 may, in some examples, providenetwork-based resources such as, but not limited to, applications forpurchase and/or download, web sites, web hosting, client entities, datastorage, data access, management, virtualization, etc. The serviceprovider devices 1130 may also be operable to provide web hosting,computer application development, and/or implementation platforms, orcombinations of the foregoing to the seller 1110 and customer 1160.

The service provider devices 1130 may be any type of computing devicesuch as, but not limited to, a mobile phone, a smart phone, a personaldigital assistant (PDA), a laptop computer, a desktop computer, a servercomputer, a thin-client device, a tablet PC, etc. The service providerdevices 1130 may also contain communications connection(s) that allowservice provider devices 1130 to communicate with a stored database,other computing devices or servers, seller terminals, and/or otherdevices on the network 1180. The service provider devices 1130 may alsoinclude input/output (I/O) device(s) and/or ports, such as for enablingconnection with a keyboard, a mouse, a pen, a voice input device, atouch input device, a display, speakers, a printer, etc.

Additionally, in some embodiments, the service provider devices 1130 maybe executed by one or more virtual machines implemented in a hostedcomputing environment. The hosted computing environment may include oneor more rapidly provisioned and released network-based resources. Suchnetwork-based resources may include computing, networking, and/orstorage devices. A hosted computing environment may also be referred toas a cloud computing environment. In some examples, the service providerdevices 1130 may be in communication with the computing devices 1112 and1162 via the networks 1180, or via other network connections. Theservice provider devices 1130 may include one or more servers, perhapsarranged in a cluster, or as individual servers not associated with oneanother.

In one illustrative configuration, the service provider devices 1130 mayinclude at least one or more processing units (or processor devices(s))1132 and at least one memory 1134. The processor device(s) 1132 may beimplemented as appropriate in hardware, computer-executableinstructions, firmware, or combinations thereof. Computer-executableinstruction or firmware implementations of the processor device(s) 1132may include computer-executable or machine-executable instructionswritten in any suitable programming language to perform the variousfunctions described.

The memory 1134 may store program instructions that are loadable andexecutable on the processor device(s) 1132, as well as data generatedduring the execution of these programs. Depending on the configurationand type of the service provider devices 1130, the memory 1134 may bevolatile (such as random access memory (RAM)) and/or non-volatile (suchas read-only memory (ROM), flash memory, etc.). The service providerdevices 1130 may also include additional removable storage and/ornon-removable storage including, but not limited to, magnetic storage,optical disks, and/or tape storage. The disk drives and their associatedcomputer-readable media may provide non-volatile storage ofcomputer-readable instructions, data structures, program modules, andother data for the computing devices. In some implementations, thememory 1134 may include multiple different types of memory, such asstatic random access memory (SRAM), dynamic random access memory (DRAM),or ROM.

Additionally, the computer storage media described herein may includecomputer-readable communication media such as computer-readableinstructions, program modules, or other data transmitted within a datasignal, such as a carrier wave, or other transmission. Such atransmitted signal may take any of a variety of forms including, but notlimited to, electromagnetic, optical, or any combination thereof.However, as used herein, computer-readable media does not includecomputer-readable communication media.

Turning to the contents of the memory 1134 in more detail, the memorymay include an operating system (O/S) 1136, code for an electronicmarketplace 1138 and code for a notification manager 1140. Thenotification manager 1140 may be configured to provide notificationfunctionalities to the seller device 1112 and the customer device 1162.These functionalities may be based on interactions with deliverydevices, active devices, passive devices, delivery management devices,and/or computing nodes of local area networks.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that various modifications and changes may be made thereuntowithout departing from the broader spirit and scope of the disclosure asset forth in the claims.

Other variations are within the spirit of the present disclosure. Thus,while the disclosed techniques are susceptible to various modificationsand alternative constructions, certain illustrated embodiments thereofare shown in the drawings and have been described above in detail. Itshould be understood, however, that there is no intention to limit thedisclosure to the specific form or forms disclosed, but on the contrary,the intention is to cover all modifications, alternative constructionsand equivalents falling within the spirit and scope of the disclosure,as defined in the appended claims.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the disclosed embodiments (especially in thecontext of the following claims) are to be construed to cover both thesingular and the plural, unless otherwise indicated herein or clearlycontradicted by context. The terms “comprising,” “having,” “including,”and “containing” are to be construed as open-ended terms (i.e., meaning“including, but not limited to,”) unless otherwise noted. The term“connected” is to be construed as partly or wholly contained within,attached to, or joined together, even if there is something intervening.Recitation of ranges of values herein are merely intended to serve as ashorthand method of referring individually to each separate valuefalling within the range, unless otherwise indicated herein, and eachseparate value is incorporated into the specification as if it wereindividually recited herein. All methods described herein may beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context. The use of any and allexamples, or exemplary language (e.g., “such as”) provided herein, isintended merely to better illuminate embodiments of the disclosure anddoes not pose a limitation on the scope of the disclosure unlessotherwise claimed. No language in the specification should be construedas indicating any non-claimed element as essential to the practice ofthe disclosure.

Disjunctive language such as that included in the phrase “at least oneof X, Y, or Z,” unless specifically stated otherwise, is otherwiseunderstood within the context as used in general to present that anitem, term, etc., may be either X, Y, or Z, or any combination thereof(e.g., X, Y, and/or Z). Thus, such disjunctive language is not generallyintended to, and should not, imply that certain embodiments require atleast one of X, at least one of Y, or at least one of Z each to bepresent.

Preferred embodiments of this disclosure are described herein, includingthe best mode known to the inventors for carrying out the disclosure.Variations of those preferred embodiments may become apparent to thoseof ordinary skill in the art upon reading the foregoing description. Theinventors expect skilled artisans to employ such variations asappropriate, and the inventors intend for the disclosure to be practicedotherwise than as specifically described herein. Accordingly, thisdisclosure includes all modifications and equivalents of the subjectmatter recited in the claims appended hereto as permitted by applicablelaw. Moreover, any combination of the above-described elements in allpossible variations thereof is encompassed by the disclosure unlessotherwise indicated herein or otherwise clearly contradicted by context.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

What is claimed is:
 1. A system, comprising: a computer systemassociated with an electronic marketplace, the computer systemconfigured to provide notifications to a user device about a delivery ofan item to a destination associated with the user device, the itemavailable from the electronic marketplace; and an active tag configuredto attach to a holder of the item for the delivery, the active tagstoring a token associated with the delivery, the token configured tofacilitate a communication between the active tag and a node of a localarea network associated with the destination, wherein: the computersystem generates a first notification for the user device about aloading of the item on a delivery vehicle, the first notification basedat least in part on a first communication of the active tag with adelivery device associated with the delivery vehicle, and the computersystem generates a second notification for the user device about adrop-off of the item at the destination, the second notification basedat least in part on a second communication of the active tag with thenode of the local area network, the second communication utilizing thetoken.
 2. The system of claim 1, wherein the computer system isconfigured to provide the token to the active tag based at least in parton an order for the item at the electronic marketplace.
 3. The system ofclaim 1, wherein the second notification about the drop-off is furtherbased at least in part on a third communication of the delivery devicewith the node of the local area network.
 4. The system of claim 1,wherein the computer system generates a third notification for the userdevice about a movement of the item at the destination, the thirdnotification based at least in part on a change of a proximity betweenthe active tag and the node.
 5. An apparatus associated with a deliveryof an item to or from a location associated with a local area network,the apparatus comprising: an interface configured to attach theapparatus to at least one of the item or a holder of the item; aprocessor; and a memory comprising computer-readable instructions that,when executed with the processor, cause the apparatus to: receive atoken associated with the local area network, the token received from acomputer system based at least in part on an order of the item processedat the computer system; store the token; establish a communication witha node of the local area network based at least in part on the token;and cause an indication of an event associated with the delivery basedat least in part on the communication with the node.
 6. The apparatus ofclaim 5, wherein the event comprises a drop-off of the item at thelocation, wherein the item is ordered from an electronic marketplace viaa user device, wherein the computer system is associated with theelectronic marketplace, wherein the computer-readable instructions, whenexecuted with the processor, further cause the apparatus to provide theindication of the drop-off to the computer system, and wherein theindication causes the computer system to provide a notification aboutthe drop-off to the user device.
 7. The apparatus of claim 5, whereinthe computer-readable instructions, when executed with the processor,further cause the apparatus to provide the indication of the event to auser device via the node of the local area network.
 8. The apparatus ofclaim 5, wherein the computer-readable instructions, when executed withthe processor, further cause the apparatus to: establish an othercommunication with a delivery device associated with a delivery vehicle,the other communication established prior to establishing thecommunication with the node; cause a notification about a start of thedelivery to be transmitted to a user device based at least in part onthe other communication with the delivery device.
 9. The apparatus ofclaim 8, wherein the item is available from an electronic marketplace,wherein the computer-readable instructions, when executed with theprocessor, further cause the apparatus to: receive instructionsassociated with the delivery from a computer system associated with theelectronic marketplace; and provide at least a portion of theinstructions to the delivery device based at least in part on the othercommunication with the delivery device, wherein the indication of theevent is based at least in part on the instructions.
 10. The apparatusof claim 8, wherein the event comprises a drop-off of the item at thelocation, wherein the computer-readable instructions, when executed withthe processor, further cause the apparatus to: receive instructionsassociated with the delivery from the node of the local area network;and authorize the drop-off to the delivery device based at least in parton the instructions, wherein the instructions are based on at least oneof: a history of past deliveries to the location, or a delivery patternassociated with other locations within a predetermined distance from thelocation.
 11. The apparatus of claim 5, wherein the apparatus comprisesan active radio frequency identification (RFID) tag configured forwireless communication with the node of the local area network, andwherein the token is configured for expiration based at least in part onone or more of: a pick-up of the item or a predefined time period from atime of a drop-off of the item.
 12. The apparatus of claim 5, furthercomprising a positioning device configured to determine geographicallocation of the apparatus, wherein the computer-readable instructions,when executed with the processor, further cause the apparatus to providethe geographical location to a user device via the node of the localarea network.
 13. The apparatus of claim 5, further comprising a sensorconfigured to sense an environmental condition associated with thelocation, and wherein the computer-readable instructions, when executedwith the processor, further cause the apparatus to provide arecommendation to the node of the local area network about a pick-up ofthe item, the recommendation causing the node to provide therecommendation to a user device associated with the local area network.14. A computer-implemented method, comprising: providing, by a computersystem to an active device, a token associated with a delivery of anitem to or from a location, the active device configured to be attachedto at least one of the item or a holder of the item for the delivery;receiving, by the computer system from a delivery device associated witha delivery vehicle, an identifier associated with the active devicebased at least in part on a proximity of the active device and thedelivery device; determining, by the computer system, a start of thedelivery based at least in part on receiving the identifier; providing,by the computer system to a user device associated with the delivery,information about the start of the delivery; receiving, by the computersystem from a node of a local area network associated with the location,an indication about an event associated with the delivery at thelocation, the indication based at least in part on a communicationutilizing the token between the active device and the node; andproviding, by the computer system to the user device associated with thedelivery, information about the event.
 15. The computer-implementedmethod of claim 14, wherein the event comprises a drop-off, and themethod further comprising: receiving a second indication about thedrop-off from the delivery device; and determining a completion of thedrop-off based at least in part on the indication from the node of thelocal area network and the second indication from the delivery device.16. The computer-implemented method of claim 14, wherein the eventcomprises at least one of: a drop-off, a lack of drop-off, a movement, alack of movement, or a pick-up, and the method further comprisingdetermining a completion of the event based at least in part on a set ofrules associated with communications between the active device, the nodeof the local area network, and the delivery device.
 17. Thecomputer-implemented method of claim 14, further comprising: receivingan image associated with event; determining a completion of the eventbased at least in part on the image; and providing, by the computersystem to the user device associated with the delivery, informationabout the completion of the event comprising the image.
 18. Thecomputer-implemented method of claim 14, further comprising determininga movement of the item based at least in part on a change of a proximitybetween the active device and the node of the local area network, theproximity based at least in part on the communication between the activedevice and the node of the local area network.
 19. Thecomputer-implemented method of claim 14, further comprising determininga pick-up of the item based at least in part on one or more of: a userinput received via the user device or a proximity between the userdevice and the active device.
 20. The computer-implemented method ofclaim 14, further comprising: providing, by the computer system,instructions to the node of the local area network or to an other nodeof the local area network based at least in part on the event, whereinthe instructions cause the node or the other node to initiate an actionof an automated device associated with the location, wherein the actionis based at least in part on the item.